This file contains late-breaking information that was not available when the Aldus FreeHand 3.1 documentation was printed. It includes:
1. information about installing Aldus FreeHand 3.1.
2. corrections to the “Guide to Installation, System 7.0 Compatibility, and Feature Updates.”
3. additional information about System 7.0 and the version 3.1 feature updates.
4. a list of the PostScript Printer Description (PPD) files that are included with Aldus FreeHand 3.1 and the printers they drive.
5. a brief explanation of the new PDX Editor.
The installation program also installs the “Aldus FreeHand 3.0 ReadMe” file, which includes corrections to the following books in the documentation set: “Aldus FreeHand 3.0 User Manual,” “Learning Aldus FreeHand,” “Making the Most of Aldus FreeHand: New Features and Tips from the Pros,” and “Aldus FreeHand and Commercial Printing.” Please read both of these files before you begin working with Aldus FreeHand version 3.1 for use with Apple Macintosh computers. We also recommend that you print copies of both ReadMe files to keep with your documentation.
-------------------------------------------
1. INSTALLING ALDUS FREEHAND 3.1
-------------------------------------------
• All current versions of Aldus FreeHand, Persuasion, PageMaker, and PrePrint use an installation program called the Aldus Installer/Utility to install program files. You should not use the version of the Aldus Installer/Utility that ships with Persuasion to install Aldus FreeHand, however. The installer for Persuasion installs key program files in a folder called “Aldus folder” in your System folder rather than in a folder called “Aldus.” Aldus FreeHand looks for program files (such as the “PANTONE Colors” file) in the Aldus folder. To avoid any problems, use the Aldus Installer/Utility provided on Disk 1 of the Aldus FreeHand 3.1 disk set to install Aldus FreeHand.
• If you’re running under System 7.0 and you’ve created an alias for the Aldus folder, you should remove the alias before installing Aldus FreeHand 3.1. Otherwise, the installer may not install all of the Aldus FreeHand files correctly.
• If you want to leave Aldus FreeHand 3.0 on your hard drive when you install Aldus FreeHand 3.1, then move the “FreeHand filters” file from the Aldus folder in your System folder into the folder with Aldus FreeHand 3.0 before you install the new version. When you install Aldus FreeHand 3.1, a new “FreeHand filters” file is installed in the folder with Aldus FreeHand 3.1. Each filters file works best with the program with which it is provided. (Note for EPS Exchange users: EPS Exchange is compatible with both version 3.0 and 3.1 of Aldus FreeHand, so you can leave this file in the Aldus folder.)
• The Aldus Installer/Utility installs program files in specific locations, such as the Aldus folder in the System folder. We recommend that you accept the default folder structure. Do not move key program files around unless you understand how Aldus FreeHand works with these files. (Aldus FreeHand looks for program files, such as the “Aldus FreeHand Defaults” file, in certain locations.)
• Because Aldus FreeHand shares a common Installer/Utility with other Aldus programs, some of the items listed on the “Diagnostics” pop-up menu do not pertain to Aldus FreeHand. One item, for example, contains the phrase “Search for printer files and Aldus Prep,” but Aldus FreeHand does not actually use “Aldus Prep.”
• If you choose to search for printer files and “Aldus Prep” during installation, the installer searches the hard drive and any file servers connected to the hard drive. To stop the search, press Command + period (.).
• During installation, information is added to the “FreeHand filters” file. This may activate virus-detecting software resident on the hard disk. To avoid the potential for error during installation, we strongly recommend that you disable or remove any virus-detecting software before installing Aldus FreeHand 3.1, and then reactivate or replace such software after the installation is complete.
• If you’ve modified your Aldus FreeHand APD files and wish to use them with Aldus FreeHand 3.1, you can move the APD files into the “PPDs” folder (located in the Aldus folder in your System folder). However, we strongly suggest that you modify the corresponding PPD files as soon as possible, and then discard the APD files. PPD files contain optimized screen angles and rulings that substantially reduce moiré patterns in color output. PPD and PDX files also allow you to calibrate imagesetter output.
• The number of PPD and PDX files present in your “PPDs” folder (located in the Aldus folder in the System folder) affects the time it takes for the “Print options” dialog box to appear when you click the “Change…” button in the printing dialog box. To reduce the time required for this dialog box to appear, install only the PPD/PDX files you need, or remove unneeded PPD and PDX files from your “PPDs” folder if you’ve already installed them.
• To install individual PPD and PDX files after you’ve installed the program, you must have the Aldus Installer/Utility installed on your hard drive. Then, locate on the installation disk set the PPD or PDX file that you want to install and double-click that file to launch the installer. The installer will prompt you to save the file to a location that you designate. We recommend saving it in the PPDs folder in the Aldus folder in your System folder.
“Installation instructions,” page 5: The instructions in the second paragraph are slightly incorrect. If you want to keep Aldus FreeHand 3.0 on your hard drive when you install Aldus FreeHand 3.1, you must separate the filters for each program to prevent conflicts. Before you install Aldus FreeHand 3.1, open the Aldus folder in your System folder. Locate the “FreeHand filters” file and move it into the folder that contains the Aldus FreeHand 3.0 program. Then, install Aldus FreeHand 3.1. You do not then need to locate and move the new “FreeHand filters” from the Aldus folder to the folder with Aldus FreeHand 3.1. The Aldus Installer/Utility will automatically install the new filters file into the folder with Aldus FreeHand 3.1.
“Installation instructions,” page 6: The instructions in the paragraph following Step 4 are incorrect. If you normally print on a QuickDraw printer, you’ll use a QuickDraw printer driver to print. You can, therefore, save room on your hard disk by not installing all of the PPDs. The Aldus Installer/Utility does require you to install at least one PPD file (such as the LWNTX470.PPD file) in order to install Aldus FreeHand, however.
“Aldus hotlinks,” page 23: The second bullet following Step 3 is incorrect. If you save a publishing file with a new name, both the original publishing file and the new file are linked to the edition file. The edition file is updated with changes from the most recently saved publishing file. To break or control the link between one of these files and the edition file, you must either move one of the publishing files to another location or open one of the publishing files, choose “Publisher options…” from the “Edition” submenu on the Edit menu, and click “Manual.” When “Manual” is selected, changes are only sent to the edition file if you choose to send them.
Note: Having more than one publishing file for an edition file complicates file management and is not recommended. If you must save a publishing file with a new name, first choose “Save” from the File menu to save the original publishing file. Then, choose “Save as…” from the File menu. If you don’t save the files in this order, you may run into problems with how the edition files link to them.
“CMYK TIFF Support,” page 60: The DCS file format is incorrectly called Desktop Color System. The correct file format name is Desktop Color Separations (DCS).
• Aldus FreeHand 3.1 is fully compatible with the new Macintosh 68040-based machines, which include the Quadra 700 and Quadra 900 series.
• Only the Macintosh IIsi, IIci, and IIfx and the new 68040-based machines currently contain the 32-bit-clean ROMs necessary to use 32-bit addressing. To set the 32-bit addressing option, choose “Control panels” from the Apple menu, double-click the “Memory” icon, and click “32-bit addressing” to turn the feature on or off. Some third party products (INITs) are available to make other Macintosh computers compatible with 32-bit addressing. Talk to your computer dealer (or call Apple Computer) for more information about these third party products.
***System 7.0 section***
• Apple recommends a standard keyboard shortcut for launching a publishing application and opening the publishing file (publisher) for a subscriber. (Once the file is open, you can edit the file and update the subscriber easily.) The recommended shortcut—pressing the Option key and double-clicking the subscriber—is used to open the various “Element info” dialog boxes in Aldus FreeHand, so we were not able to implement this keyboard shortcut.To edit the publishing file for a subscriber in Aldus FreeHand, you can select the subscriber and choose “Edit original” from the “Editions” submenu on the Edit menu, or you can select the subscriber, choose “Subscriber options…” from the Edit menu, and click “Launch Publisher.” Other Aldus applications, such as Aldus PageMaker 4.2, use Apple’s recommended keyboard shortcut.
• If you are subscribing to an Adobe PhotoShop PICT edition file from Aldus FreeHand, you may not be able to update a subscribing file with changes saved to that edition file. If this problem occurs, Aldus FreeHand will alert you when you open the subscribing file by displaying this message: “Could not complete your request because there is not enough memory.” You should then delete the subscriber and subscribe again to the updated PhotoShop PICT edition file.
• If you subscribe to an edition file, delete that edition file, and then create another edition file with the same name and in the same location, the subscriber will automatically link to the new edition file. You can use this technique to replace a subscriber automatically. Otherwise, you should avoid giving an edition file the same name and location as a deleted edition file.
• If you publish or subscribe to an edition file and then move the publishing or subscribing file to a computer with System 6.X, you cannot update the edition file to reflect changes in the publishing file or update the subscriber to reflect changes in an edition file. (A message appears when you open the file under System 6.X, alerting you that you cannot make changes to an edition file or update subscribing files with changes from an edition file.) Once you move the file back to a computer with System 7.0 and relink with the edition file, you can update the edition and subscribing files with any changes. (Aldus FreeHand prompts you to find the edition file again when you open the publishing or subscribing file under System 7.0.)
• Aldus FreeHand 3.1 and Aldus PageMaker 4.2 feature a new “hotlinks” technology that allows you to dynamically link an Aldus FreeHand EPS file (placed in either Aldus FreeHand or PageMaker) and the file from which you exported it. The command that activates the hotlink, “Edit original,” performs similarly in Aldus FreeHand and PageMaker when you’re editing placed Aldus FreeHand EPS files. However, there are also some significant differences in how the “Edit original” command works, where it’s located on the Edit menu, what keyboard shortcut activates it, and so on. Be sure to read the Aldus FreeHand 3.1 and PageMaker 4.2 documentation for a complete explanation of how the command works in each program.
• You can use the new “hotlinks” technology only to open the original illustration for an exported Aldus FreeHand EPS file and not to open the original illustration for an exported Aldus FreeHand PICT or PICT2 file.
• Balloon help may cause redraw problems for the online help system. If you have the balloon help system turned on and you open the Aldus FreeHand online help system, be careful not to move your pointer tool outside of the online help system window. If you do and a balloon opens, it temporarily erases any text that appears beneath the balloon. If you move the pointer tool over the toolbox, the text from the online help system may appear in the toolbox. To restore the screen if this happens, you should close the online help system and the toolbox and then open each of them again. To avoid these screen redraw problems, do not run the balloon help system and the online help system at the same time.
***New Features in Aldus FreeHand 3.1***
File compatibility with Aldus FreeHand 3.0 for Windows, pgs 32-34:
• If you save a file as a template in Aldus FreeHand version 3.0 for use with Microsoft Windows, and then open it in Aldus FreeHand 3.1 for the Macintosh, the file opens as a regular illustration file. You can then save it again in the template format. If you’ve installed System 7.0, you can also convert the illustration file to a stationery pad, so you can open multiple copies of it.
• If you create an illustration containing EPS, PICT, or TIFF subscribers in Aldus FreeHand 3.1 for the Macintosh, and then open that file in Aldus FreeHand for Windows, Aldus FreeHand for Windows treats those elements as PICT, TIFF, or EPS elements. You can ungroup and edit a PICT subscriber, for example, and you can choose “Element info…” from the Element menu to modify a TIFF or EPS subscriber. If you open the file on the Macintosh again, however, the subscribers are no longer linked to the edition files.
Enhanced features for creating your illustrations, pgs. 34-47
• If you’re using a WACOM digitizer with the new pressure-sensitive freehand tool, turn the tablet on before you launch Aldus FreeHand. Turning the digitizer on after launching the program may cause the “Colors,” “Layers,” and “Styles” palettes to expand to fill the illustration window.
• Aldus FreeHand uses Adobe Type Manager (ATM) 2.X to convert text to paths, so that the text converts faster. If you don’t have ATM 2.X installed on your computer, then Aldus FreeHand uses the PostScript font file to convert text to paths.
• In Aldus FreeHand 3.0, you can distort a grouped element as you transform it by selecting the grouped element, choosing “Element info…” from the Element menu, and checking “Group transforms as a unit.” Aldus FreeHand 3.1 lets you check “Group transforms as a unit” as you group the elements, saving you the extra step of opening an “Element info” dialog box. To do this, select the elements that you want to group, and then hold down the Shift key as you choose “Group” from the Element menu (or press Shift + Command + G).
• When you place an Aldus FreeHand 3.0 EPS file that contains text into an Aldus FreeHand illustration, the image you see on the screen may not match the printed version if you’re running under System 6.0 and you magnify your view of the EPS file to levels greater than 100%. (You may also experience slower redraw when you magnify your view of the EPS file.) The EPS file will print correctly, however. Aldus FreeHand 3.1 EPS files display correctly at any view under System 6.0.
• Applying a style from the “Style” submenu on the Type menu (such as “Bold” or “Italic”) to a plain text block may cause any stylized fonts (such as B Helvetica Bold) that you subsequently apply to that text to print incorrectly: Instead of printing the stylized font, Aldus FreeHand may print a plain version of the font. For example, if you apply a “Bold” style to a Helvetica text block and then you apply a B Helvetica Bold font to the same text block without changing it back to “Plain” first, the B Helvetica Bold text block may print as plain Helvetica. Once the problem occurs (you print a file and the text prints without the correct stylized font), it will reoccur in every illustration file you open until you quit Aldus FreeHand and start the program again. If you quit and start Aldus FreeHand, you can then open the file in which the problem occurred and apply the stylized font to the text again and it will print properly.
To prevent this problem from occurring, either avoid using stylized font families (use merged fonts instead), or avoid applying styles from the “Style” submenu on the Type menu (or the “Style” pop-up menu in the “Type specifications” dialog box) when you use stylized font families. If you apply a stylized font first, then the problem does not occur.
More control and speed in printing, pages 52-58
• If you have trouble printing an Aldus FreeHand file, see if you have the DeskPict INIT installed on your hard drive. We have noted occasional printing problems when this INIT is present. In general, if you have printing problems, you should check for conflicts by removing each Cdev, INIT, or Extension file one at a time, and then trying to print again.
• The System 7.0 printer driver lets you print an Aldus FreeHand illustration as a PostScript file by simply clicking “PostScript® File” for “Destination.” (You click “Printer” to print the illustration on a printer.) To open the printing dialog box, choose “Print…” from the File menu. If you are running under System 7.0, you can use this simple technique instead of the Macintosh technique described on pages 291-292 of the Aldus FreeHand 3.0 User Manual.
• The L300*.PDX (Printer Description Extension) files included with Aldus FreeHand 3.1 contain two additional paper sizes: Letter.extra.transverse - C & D and Tabloid.extra - C & D. Choose these paper sizes if you plan to print to Linotronic Cora or Densy model imagesetters. The Linotronic Cora and Densy model imagesetters have a smaller maximum image area (approximately 11.7") than more recent imagesetters (approximately 12"). If you try to print on a Linotronic Cora or Densy model imagesetter with the standard Letter.extra.transverse and Tabloid.extra paper sizes, you’ll get a PostScript error when you print.
Expanded import and export capabilities, pages 59-64
• Aldus FreeHand 3.1 allows you to export illustration files in PICT and PICT2 formats for use in other programs. These formats have inherent limitations, however, so we strongly recommend that you export your illustrations in EPS format unless you need to import it into a program that doesn’t support EPS, or you need to edit the graphic in another program. When you export an illustration in PICT or PICT2 formats, the file may lose the following information when you import it back into Aldus FreeHand or into another program:
- Graduated and radial fills
- Elements that are pasted inside other elements
- Tiled fills
- Custom and PostScript line and fill effects, which convert to solid black
- Composite paths
- Dashed strokes on paths
- Fractional point sizes applied to text
- Kerning pairs in text and manual kerning information
- Detail in curved paths that are small and complex, such as text converted to paths.
Some programs are better than others at importing information in PICT format. Aldus FreeHand, for example, does not maintain path clipping information when you import PICT files, so graduated and radial fills and elements pasted inside other elements, which are stored in the PICT file, do not appear in the imported graphic.
• When you export files in PICT format that contain any of Aldus FreeHand’s 65 patterned fills and lines, Aldus FreeHand substitutes one of the nine patterned fills or lines that the LaserWriter driver recognizes and correlates to shades of gray. This ensures the best printed results possible. This limitation only affects illustrations exported in PICT (not PICT2) format.
• If you export an Aldus FreeHand illustration in PICT or PICT2 format and then import it into Aldus Persuasion, you may get unexpected results. In Persuasion, the bounding box for the imported PICT or PICT2 graphic will be larger than the actual graphic. You must ungroup the Aldus FreeHand 3.1 PICT file to print it from the Persuasion file. If you ungroup the PICT or PICT2 graphic to edit it, however, the elements that comprise the graphic will expand to fill the enlarged bounding box.
• If you’re using a monochrome monitor when you export an Aldus FreeHand EPS file that contains colors, the EPS file will display in black-and-white on your screen when you import it into another file—even if you’ve switched to a color monitor. The EPS file will print the colors correctly, however. (If you’re using a color monitor when you export the file, then the color information will display on the screen when you place the EPS file.)
• If you export an Aldus FreeHand file in MS-DOS EPS format, Aldus FreeHand automatically unchecks the “Binary TIFF” option because MS-DOS applications cannot print binary TIFF images. You can check this option, if you want, before you export the MS-DOS EPS file.
The following list contains the names of the PPD files included with Aldus FreeHand 3.1 and the names of the corresponding printers. (The PDX files that work in conjunction with each PPD are not listed here. With the exception of the filename extension, PDX files share the same name. For example, the APPLE230.PPD works in conjunction with a PDX file called APPLE230.PDX.) For more information about PPD and PDX files, see the “Aldus FreeHand 3.0 User Manual” and the “Guide to Installation, System 7.0 Compatibility, and Feature Updates.” For information about editing PDX files, see the section “Editing PDX files” at the end of the list of PPD filenames.
S5232503.PPD Schlumberger 5232 Color PostScript Printer v50.3
S746J522.PPD Shinko Color CHC-746PSJ PostScript Printer v52.2
SCG20522.PPD Scantext 2030/51
T1513470.PPD TI OmniLaser 2115 v47.0 (13 fonts)
T1535470.PPD TI OmniLaser 2115 v47.0 (35 fonts)
TEKCP494.PPD Tektronix Phaser Card CP v49.4
TI08_450.PPD TI OmniLaser 2108 v45.0
TIm17521.PPD TI microLaser PS17 v52.1
TIm35521.PPD TI microLaser PS35 v52.1
TIx17521.PPD TI microLaser XL PS17 v52.1
TIx35521.PPD TI microLaser XL PS35 v52.1
TKPHZR21.PPD Tektronix Phaser II PXi v2010.116
TKPHZR31.PPD Tektronix Phaser III PXi v2010.116
U9415470.PPD UNISYS AP9415 (LaserPrinter15) v47.0
UNI17521.PPD UNISYS AP9210 v52.1 (17 fonts)
UNI39521.PPD UNISYS AP9210 v52.1 (39 fonts)
V5334522.PPD Varityper Series 4000/5330 v49.3/52.2
VT42P522.PPD Varityper 4200B-P v49.3/52.2
VT43P522.PPD Varityper 4300P v49.3/52.2
VT530522.PPD Varityper Series 4000/5300 v49.3/52.2
VT550522.PPD Varityper Series 4000/5500 v52.2
VT60P480.PPD Varityper VT-600P v48.0
VT60W480.PPD Varityper VT-600W v48.0
-----------------------------
5. EDITING PDX FILES
-----------------------------
Aldus FreeHand 3.1 includes a HyperCard stack called PDX Editor, which you can use to edit the PDX (Printer Description Extension) files included with Aldus FreeHand 3.1. Because all Aldus products that include PPDs (Aldus FreeHand, PageMaker 4.2, and PrePrint) use this PDX Editor, it includes editing options that Aldus FreeHand does not use. You can customize PDX files for Aldus FreeHand in these ways:
- Add custom paper sizes.
- Adjust values to calibrate imagesetter output.
To use the PDX Editor:
1. Double-click the “PDX Editor” stack icon in the Utilities folder (located in the Aldus folder in the System folder).
2. Click “Open…,” and then open the PPDs folder (located in the Aldus folder in the System folder).
3. Double-click the name of the PDX file you want to edit.
4. Click “Paper sizes” or “Calibration,” and then modify the PDX file.
5. Click “Save” to save changes. Click “Quit” to exit the PDX Editor.
For more detailed information on how to modify the “Paper size” settings or calibrate imagesetter output, click “Help” in the PDX Editor window. You can then read the information on the screen, or you can print it (by clicking “Print” in the PDX Editor window) and keep a copy with your documentation set.
If you modify a PDX file and want to restore the original file, just reinstall the original file from your installation disks.
